ci: Auto-apply 27.lts cherry-pick label to main PRs#9187
ci: Auto-apply 27.lts cherry-pick label to main PRs#9187oxve wants to merge 3 commits intoyoutube:mainfrom
Conversation
🤖 Gemini Suggested Commit Message💡 Pro Tips for a Better Commit Message:
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
The pull request introduces a new GitHub Actions configuration file to automatically apply the cp-27.lts.1+ label to all pull requests merged into the main branch. This change seems straightforward and aims to streamline the cherry-picking process for the 27.lts.1+ branch. I've reviewed the changes and found one area for improvement regarding the glob pattern.
| # These labels are automatically applied when a PR is merged. | ||
| 'cp-27.lts.1+': | ||
| - changed-files: | ||
| - any-glob-to-any-file: '**' |
There was a problem hiding this comment.
Using any-glob-to-any-file: '**' will apply the label to any change, which might be overly broad. If the intention is to only apply this label to changes that are relevant for cherry-picking to 27.lts.1+, consider a more specific glob pattern. For example, if only changes within a certain directory or with a specific file extension are relevant, the glob should reflect that. If the intent is truly for all files, then this is acceptable, but it's worth double-checking the scope.
Bug: 484351320
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| labels=$LABEL_NAME | ||
| fi | ||
| - name: Auto-label PR | ||
| uses: actions/labeler@v5 |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
1 participant
Introduce automatic labeling for pull requests merged into the main.
Changes originating on main are automatically identified as
candidates for cherry-picking to the 27.lts release branch
Additionally, update the known cherry-pick target branches to include
27.lts.1+ for other originating branches.
Bug: 484351320